home *** CD-ROM | disk | FTP | other *** search
- Path: freenet2.freenet.ufl.edu!afn03257
- From: afn03257@freenet2.freenet.ufl.edu (Daniel P Hudson)
- Newsgroups: comp.lang.c++,comp.lang.basic.misc,alt.lang.basic
- Subject: Re: Visual C++ vs Visual Basic
- Date: 19 Jan 1996 23:11:35 GMT
- Message-ID: <4dp8f7$2bf@huron.eel.ufl.edu>
- References: <4dogfq$fg2@ftcnews.nrcs.usda.gov>
- NNTP-Posting-Host: freenet2.afn.org
- X-Newsreader: wsOMR/SOUP v1.00 [NR]
-
- In article <4dogfq$fg2@ftcnews.nrcs.usda.gov>,
- ute@feinde2.ftc.nrcs.usda.gov (Ute R. Willmore) wrote:
-
-
- > Please note: This message is cross-posted to the C++ and basic group (or
- > at least I will try to cross post this thing).
- > I have been asked to evaluate Visual Basic versus Visual C++ for future
- > development needs in this shop. Since I have never seen either, I thought
- > the net might be able to give me some input.
-
- You thought wrong, at least partially. Visual Basic is NOT on topic
- in comp.lang.basic.misc and Visual C++ is NOT on topic in comp.lang.c++.
-
- VC++ q's belong in the comp.os.ms-windows.programmer.* hierarchy,
- VB-WIN belongs in the same hierarchy OR the comp.lang.basic.visual.*
- hierarchy.
-
- > What do you think?
-
- I think both langauges suck, because they run on a wannabe OS that
- can't stay running for more than an hour strait without falling into
- a endless loop of GPF's. You did ask. You want a real opinion?
- Try VC++, is should support ANSI/POSIX C and assuming this is what
- the project was written in, should be much more portable.
-